Release 4

This page is part of the FHIR Specification (v4.0.1: R4 - Mixed Normative and STU) in it's permanent home (it will always be available at this URL). The current version which supercedes this version is 5.0.0. For a full list of available versions, see the Directory of published versions . Page versions: R4 R3

4.4.2.7 HL7 v3 Code System ActPriority

Vocabulary Work Group Maturity Level: 1Draft Use Context: Any

This code system (http://terminology.hl7.org/CodeSystem/v3-ActPriority) is defined as part of HL7 v3.

Summary

Defining URL:http://terminology.hl7.org/CodeSystem/v3-ActPriority
Version:2018-08-12
Name:v3.ActPriority
Title:v3 Code System ActPriority
Definition:

A set of codes (e.g., for routine, emergency), specifying the urgency under which the Act happened, can happen, is happening, is intended to happen, or is requested/demanded to happen.

OID:2.16.840.1.113883.5.7 (for OID based terminology systems)
Source ResourceXML / JSON

This Code system is used in the following value sets:

  • ValueSet: v3 Code System ActPriority ( A set of codes (e.g., for routine, emergency), specifying the urgency under which the Act happened, can happen, is happening, is intended to happen, or is requested/demanded to happen.)

4.4.2.7.1 Code System Content

Release Date: 2018-08-12

LevelCodeDisplayDefinition
1A ASAP As soon as possible, next highest priority after stat.
1CR callback results Filler should contact the placer as soon as results are available, even for preliminary results. (Was "C" in HL7 version 2.3's reporting priority.)
1CS callback for scheduling Filler should contact the placer (or target) to schedule the service. (Was "C" in HL7 version 2.3's TQ-priority component.)
2  CSP callback placer for scheduling Filler should contact the placer to schedule the service. (Was "C" in HL7 version 2.3's TQ-priority component.)
2  CSR contact recipient for scheduling Filler should contact the service recipient (target) to schedule the service. (Was "C" in HL7 version 2.3's TQ-priority component.)
1EL elective Beneficial to the patient but not essential for survival.
1EM emergency An unforeseen combination of circumstances or the resulting state that calls for immediate action.
1P preop Used to indicate that a service is to be performed prior to a scheduled surgery. When ordering a service and using the pre-op priority, a check is done to see the amount of time that must be allowed for performance of the service. When the order is placed, a message can be generated indicating the time needed for the service so that it is not ordered in conflict with a scheduled operation.
1PRN as needed An "as needed" order should be accompanied by a description of what constitutes a need. This description is represented by an observation service predicate as a precondition.
1R routine Routine service, do at usual work hours.
1RR rush reporting A report should be prepared and sent as quickly as possible.
1S stat With highest priority (e.g., emergency).
1T timing critical It is critical to come as close as possible to the requested time (e.g., for a through antimicrobial level).
1UD use as directed Drug is to be used as directed by the prescriber.
1UR urgent Calls for prompt action.